feat: add 2026 registration flow with Google Sheets storage and confirmation email#891
feat: add 2026 registration flow with Google Sheets storage and confirmation email#891DarshanCode2005 wants to merge 65 commits intoasyncapi:masterfrom
Conversation
✅ Deploy Preview for peaceful-ramanujan-288045 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
AceTheCreator
left a comment
There was a problem hiding this comment.
Hey @DarshanCode2005 👋🏽
Thanks for the contribution! Could you add a location dropdown that lists all conference locations for users to select from?
Once that’s in, I’ll review the PR 🙏🏽
|
@AceTheCreator I’ve added the location dropdown menu. Could you please take a look and let me know if it looks good to you? |
|
Updated the types: 348cdb0 I have extended CfpForm with registration fields and remove redundant |
Both seem like relatively large packages , especially Zod. I’ll let @AceTheCreator decide whether we want to include those external dependencies or not. |
|
Okay Sir. |
|
Hi @TenzDelek Sir, I’ve been learning more about accessibility best practices and noticed some opportunities to improve the registration workflow. I’d like to enhance it by adding appropriate ARIA labels and using more semantic HTML, so screen readers and assistive technologies can support users more effectively. |
sure go ahead with the ARIA labels |
|
Hi @TenzDelek Sir, I’ve implemented several accessibility improvements across the registration workflow, including proper semantic structure, focus management, ARIA attributes, validation feedback, and screen reader announcements. I’ll continue reviewing the workflow to identify any additional improvements and will also perform more thorough testing to evaluate the WCAG rating and ensure full accessibility coverage. Please let me know if you’d like me to prioritize any specific areas. Thanks! |
|
@TenzDelek Sir, I haven’t implemented automated tests for the registration flow yet. Should I go ahead and create Cypress tests for it? I’m planning to cover the main user flow along with accessibility and validation scenarios. |
| publish = ".next" | ||
|
|
||
| [build.environment] | ||
| NODE_VERSION = "16.13.2" |
There was a problem hiding this comment.
I actually resolved the CI by changing this NODE_VERSION.
pages/register/2026/index.tsx
Outdated
| <Registration2026 /> | ||
| </main> | ||
|
|
||
| {/* Footer is rendered globally in pages/_app.tsx; avoid duplicate here */} |
TenzDelek
left a comment
There was a problem hiding this comment.
@DarshanCode2005 can you look into the conflict. ping me once it is resolved.
|
Sure sir I will look into the conflicts. And let you know. |
8743f89 to
916f328
Compare
|
I have done the changes told by you sir. Merge conflict , I have accepted the axios version bump, but I have kept the googleapis, because otherwise this current registration flow will break. |
|
@TenzDelek how we doing on this PR? |
Closes: #875
This PR introduces the Conference 2026 attendee registration flow, including backend persistence and frontend UX updates.
What’s included
New 2026 registration API (
/api/registration/2026)Google Sheets helper abstraction for safe append-only writes
Environment-based configuration for sheet ID and tab
Frontend form improvements:
Why
Notes
.env.localand credentials are intentionally excluded from version controlComplete video of the flow: https://drive.google.com/file/d/11vWbNWZ0o3IFvmUiOKxSC1u-xg10dUzo/view?usp=sharing